fix: compare Windows scheduled-import paths case-insensitively - #582
Merged
nashsu merged 1 commit intoJul 27, 2026
Merged
Conversation
Reuse the scheduled-import database path key for containment checks so drive-letter and UNC paths follow Windows case-insensitive filesystem semantics. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
nashsu
pushed a commit
that referenced
this pull request
Jul 27, 2026
…ws roots scheduledImportDestinationForFile()'s containment check compares `source === importRoot` / `source.startsWith(importRoot + "/")` case-sensitively, but Windows drive-letter and UNC paths are case-insensitive. When the source file's casing differs from the configured import root (e.g. root "C:/Users/Me/Inbox", source "c:/users/me/inbox/sub/report.pdf"), the containment check fails and the file falls back to file.name only, silently flattening its nested directory structure (and risking same-name collisions from different folders). Fix: reuse the existing drive-letter/UNC case-folding used by dbDirectoryKey (extracted into a shared caseFoldPath helper) for the comparison only; the returned path still uses the source's original casing. Verified: new test red before fix (flattened to file.name), green after; full scheduled-import.test.ts (13) and test:mocks (1679) pass; typecheck clean. Note: distinct from #582 (also open, same file) — that fixes isPathInside()'s self-import-guard case sensitivity; this fixes scheduledImportDestinationForFile()'s relative-path calculation. No functional overlap between the two. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The scheduled-import self-import guard compares normalized paths case-sensitively. On Windows, the same project can therefore appear unrelated when a drive-letter or UNC path uses different casing, allowing a project-managed directory to be selected as an external scheduled-import root.
What
Reuse the existing scheduled-import database path key for both sides of containment checks. That key case-folds drive-letter and UNC paths while leaving POSIX paths case-sensitive.
Tests
false, expectedtrue)npm run test:mocks -- src/lib/scheduled-import.test.ts(13 passed)npm run test:mocks(115 files, 1676 tests passed)npm run typechecknpm run buildDisclosure: this focused change was produced with AI assistance and validated with the regression test, full mock suite, typecheck, and production build.